Cloudflare Computer replaces the old Workspace branding across the repository. The package names, daemon name, binary name, Docker image names, examples, documentation, release workflow, and helper scripts now use the computer and computerd names consistently.

The public programming model keeps the existing Workspace shape. Types such as Workspace, WorkspaceProxy, and WorkspaceServiceProxy stay in place, and code that uses workspace.fs, workspace.shell, workspace.git, or the /workspace mount path keeps the same concepts. This keeps the rename focused on the published packages, user-facing daemon, repository identity, and release artifacts rather than changing the API model at the same time.

The rename also updates the container path between the durable object and computerd: the default callback host is now computer.internal, and the daemon endpoints use the computerd name. The release workflow now builds and stages computerd-linux-x64, publishes @cloudflare/computer, and pushes the renamed computer-computerd-linux-x64 images.

Documentation and examples now install and import @cloudflare/computer, use @cloudflare/computer-rpc for the wire package, and refer to the daemon as computerd. The repository guidance, package READMEs, examples, benchmark scripts, and Dockerfiles were updated to match the new names while keeping intentional npm workspace and /workspace terminology.

Verified with:

npm run build
npm run typecheck
npm test
npm run format
npm run check
cd packages/computer && npx vitest run src/backends/container/cloudflare-container.test.ts src/backends/container/container-lifecycle.test.ts

The old branded package, repository, Docker image, binary, and workspace.internal names no longer appear in tracked files, aside from intentional API and npm workspace terminology.